WebDav destination module
With the WebDAV module, a file can be stored in a WebDav folder. The module can occur several times in the workflow. The access data defined in this dialog is used to gain access to the destination directory.
You can use variables in all input fields, see Variables.

The module can occur several times in the workflow.

The module can be connected to all modules (this can result in nonsensical workflows).

No restrictive modules.


This field is used to specify the name that the scan file should be given.

With this switch you can specify whether a timestamp consisting of the date and time is to be appended to the name from File Name. Alternatively, you can use date and time variables in the File Name field.

Enter the web address of the server that runs WebDav (e.g. http://webdavserver).

The alias is the virtual directory of the WebDav server. Enter only the name of the virtual directory here, i.e. for http://webdavserver/VirtualDirectory, only VirtualDirectory).

The virtual directory specified under Alias points to a physical path that can be located on the WebDav server itself (e.g. c:\webdav) or on another server (e.g. \\fileserver\webdavDirectory).
In this field, specify the subfolder of this directory. For example, if you specify files, the file is stored in the directory \\fileserver\webdavdirectory\files. The last directory is created automatically if it does not exist. This also applies if a directory structure is specified under Directory (e.g. files\user) - in this case, however, only the last directory (user) can be created and not the directory structure (files\user).

The username for accessing the directory on the target server must be entered in this field.

The user's password must be entered in this field (for access to the directory on the target server).


The ImageService processes image data (e.g. from scans) and performs file format conversions, image optimization and the OCR function. It stores files in desired destination directories (depending on the module used, the rights of the user executing its application pool are used for this purpose). Its log file is Logs\ImageService.log.